Mobile device power management in data synchronization over a mobile network with or without a trigger notification

ABSTRACT

A method for transferring data between a mobile device and a client includes sending transactions from the mobile device to the client over a first connection and determining how often to receive new data.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a Continuation of U.S. patent application Ser. No.14/623,514, filed Feb. 17, 2015, entitled “CONNECTION ARCHITECTURE FOR AMOBILE NETWORK, which is a continuation of U.S. patent application Ser.No. 11/470,802, filed Sep. 7, 2006, entitled “CONNECTION ARCHITECTUREFOR A MOBILE NETWORK,” which is a Continuation of U.S. application Ser.No. 10/339,368, filed Jan. 8, 2003, entitled CONNECTION ARCHITECTURE FORA MOBILE NETWORK, now U.S. Pat. No. 7,139,565, which claims the benefitof both U.S. Provisional Application No. 60/346,881 filed Jan. 8, 2002and U.S. Provisional Application No. 60/403,249 filed Aug. 12, 2002, allof which are herein incorporated by reference in their entirety.

BACKGROUND

Mobile email messaging systems typically use a store and forwardarchitecture. Electronic Mail (email) redirector software runs either onan enterprise email server or on a desktop computer. The redirectorsoftware monitors a user mailbox. When a new email message is receivedin the mailbox, the redirector makes a copy of the email message andwraps the copy in an encryption envelope and encapsulates the copy fordelivery to the mobile device. The redirector may optionally encryptand/or digitally sign the encapsulated email message.

The encrypted encapsulated email message is sent out over the Internetand routed to a mobile device associated with the user mailbox. Ifencrypted, the email message is decrypted by the mobile device prior tobeing stored on the mobile device and then displayed and stored on themobile device. This same process is repeated for every new email that isreceived in the user's mailbox.

Thus, with this architecture two versions of the same mailbox exist. Theprimary mailbox on the email server or desktop PC, and the replicatedmailbox on the mobile device. Consistency between the primary and thereplicated mailbox may be maintained to some degree usingsynchronization messages passing back and forth between the redirectorand the mobile device. For example, an email message deleted from themobile device may result in a synchronization message to the desktopredirector, which instructs it to also delete that message from theprimary mailbox. In some versions of this architecture, no effort at allis made to ensure consistency of mailbox state between the primary andreplicated instances. This store and forward architecture is cumbersome,does not operate in real-time, and requires sending a large number ofemail messages over the Internet. The present invention addresses thisand other problems associated with the prior art.

SUMMARY

A real-time communication architecture establishes a continuousconnection between an enterprise network and a communication managementsystem. The connection is continuously held open allowing mobile devicesreal-time access to enterprise data sources such as email systems. Thereal-time communication architecture can support an entire enterpriseemail system or individual email users.

The foregoing and other objects, features and advantages of theinvention will become more readily apparent from the following detaileddescription of a preferred embodiment of the invention which proceedswith reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a mobile communication architectureaccording to one embodiment of the invention.

FIG. 2 is a block diagram of an enterprise version of the communicationarchitecture.

FIG. 3 is a block diagram showing how transactions are transferred inthe communication architectures shown in FIGS. 1 and 2.

FIG. 4 is a block diagram showing how local network files are viewed andselected by a mobile device.

FIG. 5 is a block diagram showing how data is stored in a mobile device.

FIG. 6 is a block diagram showing how the mobile device is synchronized.

DETAILED DESCRIPTION

For simplicity, data, databases, files, and data transactions may bereferred to generally as Electronic mail (email), email transactions,mailboxes, etc. However, it should be understood that any type of emaildata or email transaction described below can be similarly performed forcalendars, contacts, tasks, notes, electronic documents, files or anyother type of data that needs to be transferred between a local networkand a mobile device,

FIG. 1 shows one embodiment of a real-time communication architecture 12that includes a mobile network 14, an enterprise network 18, and acommunication management system 16 that manages communications betweenthe mobile network 14 and the enterprise network 18.

The enterprise network 18 in one instance is a private network thatcontains a firewall 31. The firewall 31 can be a set of relatedprograms, located at a network gateway server that protects theresources of the enterprise network 18 from users from other networks.The term ‘firewall’ also implies the security policy that is used withthe firewall programs.

The mobile network 14 includes mobile devices 21 that communicate overthe Internet through a wireless or landline mobile network 14. Sincemobile networks 14 are well known, they are not described in furtherdetail.

The enterprise network 18 can be any business network, individual usernetwork, or local computer system that maintains local email or otherpersonal data for one or more users. In the embodiment shown in FIG. 1,the enterprise network 18 includes an email server 34 that is accessedby multiple Personal Computers (PCs) 38. In one example, the emailserver 34 may be a Microsoft® Exchange® server and the PCs 38 may accessemail on the email server 34 through a Microsoft® Outlook® softwareapplication. The email server 34 can store email mailboxes, contactlists, calendars, tasks, notes, or any other type of local data orelectronic document.

The PC 38 is connected to the email server 34 over a Local Area Network(LAN) 35. The PC 38 includes memory 39 for storing local files that mayinclude personal email data as well as any other types of electronicdocuments. Personal client software 40 is executed by a processor in thePC 38. The personal client 40 exchanges transactions with the mobiledevice 21 for browsing email, calendars, and contact information as wellas accessing local files.

A communication management system 16 includes at least one managementserver 28 that manages the transactions between the mobile device 21 andthe enterprise network 18. A user database 42 includes configurationinformation for different users. For example, the user database 42 mayinclude login data for user's in enterprise network 18.

Enterprise Version

FIG. 2 shows an enterprise version of the communication architecture 12.The enterprise network 18 includes an enterprise server 34 that connectsthrough LAN connection 35 to multiple PCs 38. The enterprise server 34also includes an enterprise client 41 that can communicate directly withthe management server 28.

The communication management system 16 in FIG. 2 includes the managementserver 28, as well as one or more Smart Device Servers (SDS) 30, and oneor more Personal Client Servers (PCS) 32. The SDS 30 handlescommunications with particular smart mobile devices 24. The PCS 32manages communications with personal clients 40.

The mobile devices 21 in FIG. 2 are shown in more specificity andinclude cell phones 20 having WAP interfaces that communicate withmanagement server 28 through a WAP gateway 26. Other mobile devices 21may include PCs, PDAs, Internet kiosks 22, or any other smart mobiledevice 24 that operates as communication endpoints.

Mobile connection 23 in FIG. 1 and mobile connections 45, 46 and 44 inFIG. 2 are any connections that allow the mobile devices 21 tocommunicate over the Internet. For example, the connections 23, 44, 45and 46 may be through landlines, cellular channels, 802.11 wirelesschannels, satellite channels, etc.

Continuous Real-Time Connectivity

Referring specifically to FIG. 1, the personal client 40 automaticallyestablishes a continuous connection 25 between the PC 38 and managementserver 28. The personal client 40 initiates an outbound connection 25which is then authenticated by the management server 28. For example,the client 40 presents an authentication token 29 to the managementserver 28. The management sever 28 then attempts to match theinformation in the authentication token 28 with information in userdatabase 42.

If the authentication token 29 is authenticated, the connections 25 or48 are established through the firewall 31 to achieve access to themanagement server 28 which is outside the private enterprise network 18.The management server 28 then sends the personal client 40 connectionauthorization and any other needed information. For example, themanagement server 28 may send back connection sharing information, emailnotification filters, and other mobile communication configurationparameters associated with a particular user.

The management server 28 and the personal client 40 then go into aquiescent mode until a transaction, such as a data query, is transferredbetween the mobile device 21 and the personal client 40. If for anyreason the connection 25 is disconnected, the personal client 40automatically establishes another connection 25 with management server28.

It is important to note that the connection 25 is continuouslymaintained even when no connection 23 is currently exists between mobiledevice 21 and management server 28. In one embodiment, the connection 25is a Transmission Control Protocol/Internet Protocol (TCP/IP)connection. However, any connection protocol can be used that allowscontinuous connectivity between the enterprise network 18 andcommunication management system 16.

In an alternative embodiment, the connection 25 may be establishedthrough a proxy server (not shown) in enterprise network 18. Forexample, messages sent by the personal client 40 may be encrypted by theproxy server with a Secure Sockets Layer (SSL).

After the connection 25 is established by the personal client 40, amobile connection 23 can be established at any time between the mobiledevice 21 and the management server 28. After the mobile connection 23is established, the mobile device 21 can then access email and otherinformation in the email server 34 or memory 39 through personal client40. Thus, after connection 25 is established, the personal client 40effectively operates as an email server for the mobile device 21.

Referring to FIG. 2, in a manner similar to the personal client 40, anenterprise client 41 establishes a continuous connection 48 with themanagement server 48 similar to the connection 25 established betweenthe personal client 40 and management server 28. The connection 48 isused for relaying transactions between multiple mobile devices 21 andmultiple email users on enterprise server 34 at the same time.

In the version of the communication architecture shown in FIG. 2, thepersonal client 40 may establish connection 25 with the managementserver 28 through PCS 32 and certain mobile devices 24 may establishmobile connections 44 through the SDS 30.

Mobile Device Log-In

Referring to FIGS. 1 and 2, the management server 28 authenticatesmobile connections 23, 44, 45, and 46 initiated by the mobile devices21. When a user signs up for a mobile account, a copy of the user'susername and password for the enterprise network 18 is stored in theuser database 42. After the mobile device 21 powers on, the user isrequired to login to the communication management system 16 by enteringanother user name and password. If the mobile device 21 accesses emailthrough the enterprise server 34, as opposed to through the PC 38, thenan enterprise identifier (e.g., name) may also be required.

The mobile device 21 sends an authentication token 27 either directly tothe management server 28 or to the SDS 30 which forwards theauthorization token 27 to the management server 28. The managementserver 28 verifies information in the authorization token 27 withinformation in the user database 42. If the authentication token 27 isverified, the management server 28 sends an authorizationacknowledgement directly to the mobile device 21 or through the SDS 30.

Once the mobile device 21 has successfully logged in, the managementserver 28 unlocks the user's enterprise user name and password. Thisallows the mobile device 21 to access email and other local files in theenterprise network 18 either through connection 25 or connection 48.

The management server 28 also conducts rendering and view functionsneeded for presenting email and other data to the different mobiledevices 21. For example, the management server 28 reformats local dataretrieved from the enterprise network 18 according to the particularmobile device 21 requesting the information. The management server 28also operates as a transactional routing engine for routing transactionsbetween the mobile devices 21 and the enterprise network 18.

Stateless Non-Replicated Connectivity

Referring to FIG. 3, once the mobile device 21 has successfully loggedin, stateless connectivity exists between the mobile device 21 and thepersonal client 40 over connections 23 and 25. For example, the mobiledevice 21 may send a transaction request 62 to the personal client 40 toview emails in the users mailbox 60.

The transaction request 62 is sent from the mobile device 21 to themanagement server 28 over mobile connection 23. The management server 28locates the personal client 40 associated with request 62 and forwardsthe request 62 over the appropriate connection 25. The personal client40 accesses data in mailbox 60 according to the transaction request 62.For example, if the transaction request 62 requests viewing the user'slatest emails, the personal client 40 generates an email list 64containing the emails received in mailbox 60. The personal client 40then sends the email list 64 back to the mobile device 21 throughconnection 25.

If the mobile device 21 has limited memory or viewing capability, only alatest portion of the emails in mailbox 60 may be included in email list64. Alternatively, the personal client 40 may send all of the emails inmailbox 60 to the management server 28. The management server 28 thendoles out portions of the email list 64 to the mobile device 21according to the type of electronic platform used by the mobile device21.

These transactions allow the mobile device 21 to view information inmailbox 60 in real time without having to maintain a second version ofthe emails in mailbox 60. Once the connection 23 is terminated, theemail list 64 received by the mobile device 21 may be deleted. If emailsin mailbox 60 need to be viewed again, the mobile device 21 sends a newtransaction request 62 to the personal client 40.

If the items requested in transaction 62 are too numerous or too largefor viewing by the mobile device 21, the personal client 40 may sendonly enough information in list 64 to identify the items. For example,the personal client 40 may glean out from an email the email senderinformation, when the email was sent, and the subject line. The personalclient 40 may only send out this gleaned information for the latestemails received in mailbox 60.

The mobile device 21 receives the gleaned partial list 64 and can thenselect one or more of the items in list 64 for viewing. Depending on thetype of data requested for viewing, another transaction request 62 maybe sent from mobile device 21 to personal client 40 to view the selectedemail in its entirety. The personal client 40 then sends any remainingcontents of that selected email to the mobile device 21. Alternatively,if the gleaned partial email list 64 does not contain the email that themobile device user wishes to view, the mobile device 21 can send anothertransaction request 62 to the personal client 40 to view a secondportion of the emails contained in mailbox 60.

After the transaction between the mobile device 21 and the managementserver 28 is completed, no emails from mailbox 60, or any other filesfrom the PC 38 need to remain on the mobile device 21. That is unlessthe mobile device 21 saves a copy of the data. Thus, the servers 28, 30and 32 and the mobile devices 21 shown in FIGS. 1-2 do not have tomaintain a second version of the email data in mailbox 60.

This stateless connectivity does not require the large number oftransactions that are typically required in store and forwardarchitectures and also eliminates having to copy emails and send thecopies to the mobile device each time an email is received at the user'smailbox.

Local Data File Access

FIG. 4 shows how the mobile device 21 accesses local files contained onthe PC 38 and attaches those local files to email messages. The personalclient 40 operating on PC 38 is initially configured to point to a rootdirectory 80. The root directory 80 may include multiple subfolders 82that contain files 84 and 86. Other files 88 and 90 may be located atthe top level of the root directory 80 or located in other subfolders.

Some mobile devices 21 may not have the capability to actually open andread the files in root directory 80 or there may be too much data incertain files for the mobile device 21 to store. In these situations,the mobile device 21 can still view, navigate and select folders andfiles located under the root directory 80.

An email message 70 is opened on the mobile device 21. An Insert Fileoption may then be selected in the email application running on themobile device 21. Selecting the Insert File option sends a view filestransaction 76 from the mobile device 21 to the management server 28.

The management server 28 sends the transaction 76 over the appropriateconnection 25 to personal client 40. The personal client 40 receives thetransaction 76 and determines the mobile device 21 has requested a listof files in root directory 80. The personal client 40 generates aresponse containing a file list 78 identifying the subfolders 82 andfiles 84-90 in root directory 80. The response message containing filelist 78 is then sent back to the mobile device 21 over connection 25.

All or part of the file list 78 may be sent to mobile device 21. Forexample, the management server 28 may determine the mobile device 21 hasinsufficient memory to view the entire file list 78. The managementserver 28 could also determine it would take too much time to send theentire file list 78 to the mobile device 21. In these cases, themanagement server 28 may only send a portion of the file list 78 to themobile device 21.

The mobile device 21 displays the file list 78 received from themanagement server 28 and selects any of the listed files or subfolders.A subfolder in the file list 78 may be selected that contains files notincluded in the file list 78. This causes the mobile device 21 to sendout another view file transaction 76 to the management server 28requesting a list of the files contained in the selected subfolder. Themanagement server 28, or personal client 40, then sends back anotherfile list 78 containing the files in the selected subfolder.

If one or more files are selected from the file list 78, an associatedfile identifier 72 is inserted into the email message 70. In oneexample, selecting files is equivalent to a Hypertext Markup Language(HTML) forms submission where an item is selected from a website. Whenan email Send command is selected on the mobile device 21, an emailtransaction 74 is sent to the management server 28 that includes emailmessage 70 and file identifier 72.

The management server 28 sends the email transaction 74 throughconnection 25 to the personal client 40. In the enterprise network shownin FIG. 2, the email transaction 74 may travel from the SDS 30 to themanagement server 28 and then through the PCS 32 and connection 25 tothe personal client 40.

The personal client 40 unwraps the email transaction 74 and extracts theemail message 70 containing the file identifier 72. The personal client40 reformats the email message 70 into an email message 92 and thenattaches the file in root directory 80 corresponding to file identifier72. The email message 92 with the attached file is then sent by thepersonal client 40 to the email server 34. A copy of the email message92 may also be copied to the Sent Items folder in the user's mailbox.

Storing Queries

Referring to FIG. 5, some mobile devices 21 referred to as smart mobiledevices may include software that operates a mobile client 98 thatreceives and transmits data. The mobile device 21 can store anotherversion of the local data in email server 34. The stored data caninclude contact information stored in memory section 100, emails storedin memory section 102 and calendar information stored in memory section104. The mobile device 21 can view, generate emails, and generallymanipulate the data in memory section 100-104 off-line.

The mobile client 98 can maintain a latest version of queried data inmemory section 100-104 using the stateless connectivity architecturedescribed above. For example, when a View Contacts operation isinitiated on the mobile device 21, the mobile client 98 sends a viewcontacts transaction 106 to the personal client 40. The mobile device 21may have requested the contacts list 114 for the entire enterprisenetwork. If the contacts list 114 is too large to send to the mobiledevice 21, the personal client 40 may only send back a first portion 108of the contacts list. For example, a list of contacts for the first fewletters of the alphabet.

If the contact the user is looking for is not within the first contactslist portion 108, the user can send a second View Contacts transaction110 to the personal client 40. The second transaction 110 may identify aspecific letter of the alphabet for the personal client 40 to query.Alternatively, the transaction 110 may direct the personal client 40 tosend back a next portion of the enterprise contact list 114 immediatelyfollowing contacts list portion 108. The personal client 40 sends back asecond portion 112 of contact list 114 pursuant to the transactions 110.If the contact the user is looking for is in the second contact listportion 112, no further queries are sent from the mobile device 21.

The mobile client 98 can store the last received contact list portion112 in memory 100. According to the amount of memory available in themobile device 21, the mobile client 98 may save the last few contactlist portions 112 and 108 in memory 100. Thus, when the mobile device 21goes off-line, a user is still able to view the latest informationreceived from personal client 40. The mobile client 98 can also save themost recent email queries in memory space 102 and the most recentcalendar queries in memory space 104.

Synchronization

Referring to FIG. 6, the mobile device 21 may store a second version 122of the user's local data. It may be necessary from time to time tosynchronize the second version 122 on the mobile device 21 with thelocal version 136 on the email server 34. In one embodiment, the mobiledevice periodically sends out synchronization requests 134 to thepersonal client 40. The personal client 40 generates a response 133pursuant to the synchronization request 134 that contains the latestemails, or other local user data. The response 133 is sent back to themobile device 21 and is used for updating data 122.

Triggers can be used to notify the mobile device 21 when new emailsarrive on the email server 34. Filters 138 are configured in thepersonal client 40 that identify the types of emails or other types ofevents that cause the mobile device 21 to send a trigger 132.

For example, the filters 138 may tell the personal client 40 to send atrigger 132 each time a new email arrives in the user's mailbox. Thepersonal client 40 monitors the user's mailbox in email server 34 fornew emails. If a new email is detected, the personal client 40 sends atrigger 132 to the mobile device 21 through the management server 28.The trigger 132 may be a message with no payload that simply tells themobile device 21 that something new has happened in the user's mailbox.The trigger 132 causes the mobile device 21 to establish the mobileconnection 23 with the management server 28 and then send asynchronization request transaction 134 to the personal client 40.

In one implementation, Short Message Service (SMS) messages 126 are usedto trigger the mobile device 21 into establishing the mobile connection23 and send the synchronization request transaction 134. The managementserver 28 is coupled through a notification gateway 130 to a ShortMessage Service Controller (SMSC) 128 operated by a mobile communicationservice carrier. In other implementations, some other notificationprotocol, such as a Wireless Application Protocol (WAP) Push is used totrigger the mobile device 21.

The personal client 40 generates the trigger message 132 whenever anevent associated with the user's mailbox 136 corresponds with an eventidentified in filters 138. The trigger message 132 causes the managementserver 28 to send a message through the notification gateway 130 to theSMSC 128. The SMSC 128 accordingly sends the SMS message 126 to themobile device 24.

The mobile device 21 monitors for particular SMS messages having someparticular computer readable content. When SMS message 126 is receivedhaving that particular content, the mobile device 21 initiates a mobileconnection with management server 28. The mobile device 21 may extractthe SMS message 126 from a user queue before a user has a chance to seeit.

The mobile device 21 initiates an authentication process with themanagement server 28. After successful authentication, thesynchronization request 134 is sent from the mobile device 21 to themanagement server 28. The management server 28 transfers the request 134to the personal client 40 over the previously established connection 25.The personal client 40 upon receiving the synchronization request 134sends back a response 133 that includes a list of the latest emails inthe user's mailbox 136.

High Priority Email

Still referring to FIG. 6, the connection architecture shown above canalso be used for providing notification of high priority emails. Thepersonal client 40 may be configured to monitor the email server 34 forparticular types of email messages. For example, the filters 138 maycause the personal client 40 to look for any emails sent from aparticular sender email address. For example, email sent from the user'ssupervisor.

Whenever an email arrives in the user's mailbox 136 sent from thesupervisor's email address, the personal client 40 sends a stripped downversion of that email through the management server 28 to the SMSC 128.For example, the stripped down version may only identify the sender,time, date, and subject line for the email message. The SMSC 128 thensends a SMS high priority message 124 to the mobile device 24.

The stripped down high priority SMS message 124 may be slightlydifferent than the SMS message 126 used for triggering mobile devicesynchronization. For example, the SMS message 126 may not contain anyemail content, while the priority message 124 includes some portion ofthe actual email content received in mailbox 136. The high prioritymessage 124 can be sent to any SMS capable mobile device.

Power Management

The mobile device 21 can periodically initiate synchronization accordingto an amount of charge remaining in a battery 123. For example, whenbattery 123 has a relatively large amount of charge remaining, themobile device 21 may synchronize more frequently than when the battery123 has a relatively small amount of charge remaining Systems fordetermining an amount of charge remaining in battery are well known andare therefore not described in further detail.

Different charge gradient levels can be used for varying how often themobile device 21 synchronizes with the personal client 40. For example,the mobile device 21 may synchronize every 5 minutes when the battery123 has 75% or more charge remaining and may synchronize every 10minutes when the battery 123 is between 75% and 50% charged. When thebattery 123 is between 50% and 25% charged, the mobile device 21 mayonly synchronize with personal client 40 every 30 minutes. Othercharge/synchronization rates can also be used.

To further conserve power, synchronization can be varied according tothe day of the week. For example, the mobile device 21 may synchronizeless often on weekends than on weekdays.

SUMMARY

The system described above can use dedicated processor systems, microcontrollers, programmable logic devices, or microprocessors that performsome or all of the operations. Some of the operations described abovemay be implemented in software and other operations may be implementedin hardware.

For the sake of convenience, the operations are described as variousinterconnected functional blocks or distinct software modules. This isnot necessary, however, and there may be cases where these functionalblocks or modules are equivalently aggregated into a single logicdevice, program or operation with unclear boundaries. In any event, thefunctional blocks and software modules or features of the flexibleinterface can be implemented by themselves, or in combination with otheroperations in either hardware or software.

Having described and illustrated the principles of the invention in apreferred embodiment thereof, it should be apparent that the inventionmay be modified in arrangement and detail without departing from suchprinciples. We claim all modifications and variation coming within thespirit and scope of the following claims.

We claim:
 1. A method for transferring data between a mobile device anda host, comprising: sending, in response to instructions from aprocessor, application data requests from a mobile device to a host overa first connection at a first frequency; receiving data from the hostresponsive to the sent application data requests; selecting a powermanagement mode, from a plurality of power management modes, based on anamount of battery power remaining on the mobile device, whereinselecting a power management mode is further based on the amount ofbattery power remaining being below a predetermined amount; changing thefrequency that the application data requests are sent from the firstfrequency to a second frequency associated with the selected powermanagement mode; wherein at least two of the power management modes area low power mode configured to conserve the amount of battery powerremaining on the mobile device and a normal operation mode, wherein thenormal operation mode is configured to allow the mobile device to sendapplication data requests more frequently than when the mobile device isin low power mode, wherein the frequency at which some application datarequests are sent is not changed to the second frequency while themobile device is in the low power mode; and exiting the low power modewhen an amount of battery power remaining is above a predeterminedamount.
 2. The method of claim 1, further comprising: receiving atrigger that notifies the mobile device of new data; and receiving newdata from the host, wherein receiving the new data from the host is atleast in part responsive to the trigger, wherein the new data is of atype for which a trigger is to be sent, and wherein the trigger causesthe mobile device to send at least one data request associated with thetrigger.
 3. The method of claim 1, wherein the predetermined amount is75% of battery charge.
 4. The method of claim 1, wherein the mobiledevice sends application data requests periodically.
 5. The method ofclaim 1, further comprising authenticating a user of the mobile deviceover the first connection, wherein authenticating a user is performed bysending an authentication token.
 6. The method of claim 1, furthercomprising authenticating a user of the mobile device by sending anauthentication token over the first connection, wherein theauthentication token is verified against a user database.
 7. The methodof claim 6, wherein authenticating the user allows the mobile device toaccess content at the host.
 8. The method of claim 1, further comprisingreceiving a notification of new content.
 9. The method of claim 8,wherein the notification is received over a connection that ismaintained while the mobile device is in the power management mode. 10.The method of claim 8, wherein the notification includes a portion of acontent that is to be received by the mobile device.
 11. The method ofclaim 8, wherein the notification includes less than a totality of thecontent to be received by the mobile device.
 12. The method of claim 8,further comprising establishing a subsequent connection for receipt ofthe content.
 13. The method of claim 8, wherein the notificationincludes an identification of a sender of the content.
 14. The method ofclaim 8, further comprising displaying the notification on the mobiledevice for viewing by the user.
 15. A mobile device located in a mobilenetwork, comprising: a battery; a processor configured to allow themobile device to: send application data requests to a host over a firstconnection at a first frequency; receive data from the networkresponsive to the sent application data requests; select a powermanagement mode from a plurality of power management modes based on anamount of battery power remaining on the mobile device, wherein theselection of a power management mode is further based on the amount ofbattery power remaining being below a predetermined amount; change thefrequency that application data requests are sent from the firstfrequency to a second frequency associated with the selected powermanagement mode; wherein at least two of the power management modes area low power mode configured to conserve the amount of battery powerremaining on the mobile device and a normal operation mode, wherein thenormal operation mode is configured to allow the mobile device to sendapplication data requests more frequently than when the mobile device isin the low power mode, wherein the frequency at which some applicationdata requests are sent is not changed to the second frequency while themobile device is in the low power mode; and exit the low power mode whenan amount of battery power remaining is above a predetermined amount.16. The mobile device of claim 15, wherein at least one of the powermanagement modes uses charge gradient levels for determining how oftento send application data requests.
 17. The mobile device of claim 15,wherein at least one of the power management modes is configured toallow the mobile device to send application data requests lessfrequently on weekends than on weekdays.
 18. The mobile device of claim15, wherein the processor is further configured to allow the mobiledevice to: receive a trigger that notifies the mobile device of newdata; and receive the new data from the host, wherein receiving the newdata from the host is at least in part responsive to the trigger, andwherein the trigger is received by the mobile device when the new datais of a type for which a trigger should be sent, wherein the triggercauses the mobile device to send at least one data request associatedwith the trigger.
 19. The mobile device of claim 15, wherein thepredetermined amount is 75% of battery charge.
 20. The mobile device ofclaim 15, wherein the sent application data requests occur at a firstfrequency when the mobile device is in a normal operation mode, and at asecond frequency when the mobile device is in the low power mode,wherein the first frequency is higher than the second frequency.
 21. Themobile device of claim 15, wherein the application data requests aresent periodically.
 22. The mobile device of claim 15, wherein theprocessor is further configured to allow the mobile device toauthenticate a user of the mobile device over the first connection bysending an authentication token.
 23. The mobile device of claim 15,wherein the processor is further configured to allow the mobile deviceto authenticate a user of the mobile device by sending an authenticationtoken over the first connection, wherein the authentication token isverified against a user database.
 24. The mobile device of claim 23,wherein authenticating the user allows the mobile device to accesscontent at the host.
 25. The mobile device of claim 15, wherein theprocessor is further configured to allow the mobile device to receive anotification of new content.
 26. The mobile device of claim 25, whereinthe notification is received over a connection that is maintained whilethe mobile device is in the power management mode.
 27. The mobile deviceof claim 25, wherein the notification includes a portion of a contentthat is to be received by the mobile device.
 28. The mobile device ofclaim 25, wherein the notification includes less than a totality of thecontent to be received by the mobile device.
 29. The mobile device ofclaim 25, wherein the processor is further configured to allow themobile device to establish a subsequent connection for receipt of thecontent.
 30. The mobile device of claim 25, wherein the notificationincludes an identification of a sender of the content.
 31. The mobiledevice of claim 25, wherein the notification is displayed on the mobiledevice for viewing by the user.
 32. A mobile device located in a mobilenetwork, comprising: a battery; a processor configured to allow themobile device to: monitor a remaining battery level of the battery; sendapplication data requests to a host over a first connection at a firstfrequency; receive data from the host responsive to the sent applicationdata requests; operate in a normal operations mode when a remainingbattery level is above a predetermined amount; select a low power modefrom a plurality of power management modes in order to conserve theremaining battery level when the remaining battery level is below thepredetermined amount, wherein the low power mode is based on amount ofbattery power remaining on the mobile device being below a predeterminedamount; change the frequency that application data requests are sentfrom the first frequency to a second frequency associated with the lowpower management mode; wherein at least two of the power managementmodes are the low power mode configured to conserve the amount ofbattery power remaining on the mobile device and the normal operationsmode, wherein the normal operation mode is configured to allow themobile device to send application data requests more frequently thanwhen the mobile device is in the low power mode, wherein the frequencyat which some application data requests are sent is not changed to thesecond frequency while the mobile device is in the low power mode; exitthe low power management mode when the remaining battery level is abovethe predetermined amount; and receive a trigger that notifies the mobiledevice of new data, wherein the trigger at least in part causes themobile device to send application data requests.
 33. The mobile deviceof claim 32, wherein the processor is configured to allow the mobiledevice to enter the low power mode when the amount of battery powerremaining is below a predetermined amount.
 34. The mobile device ofclaim 32, wherein the processor is further configured to allow themobile device to receive a notification of new content.
 35. The mobiledevice of claim 32, wherein the notification is received over aconnection that is maintained while the mobile device is in the powermanagement mode.
 36. The mobile device of claim 34, wherein thenotification includes a portion of a content that is to be received bythe mobile device.
 37. The mobile device of claim 34, wherein thenotification includes less than a totality of the content to be receivedby the mobile device.
 38. The mobile device of claim 34, wherein theprocessor is further configured to allow the mobile device to establisha subsequent connection for receipt of the content.
 39. The mobiledevice of claim 34, wherein the notification includes an identificationof a sender of the content.
 40. The mobile device of claim 34, whereinthe notification is displayed on the mobile device for viewing by theuser.